Operational Considerations NEW!

Consider the following when you use Node Alias:

• By default, the switch enables Node Alias globally, as well as on Auto-sense enabled ports. If you disable Node Alias globally, port level functionality is also disabled. If the ports are combined to form an MLT (LAG), you must enable or disable Node Alias on individual ports.
• You cannot enable Node Alias on SPBM NNI ports.
• You cannot enable Node Alias on Extreme Integrated Application Hosting ports.
• The protocol information database stores detailed information for IPv4, IPv6, BGP, VRRP, and UDP only.
• DHCP Fingerprinting is integrated into Node Alias functionality; therefore, you must enable Node Alias to perform DHCP Fingerprinting.
• The maximum number of Node Alias clients is on per switch, not per port.
• The number of clients stored in the Node Alias client database cannot be lower than the number of existing clients.
• If you do not explicitly clear entries when the client database is full, inactive entries automatically clear first followed by the first oldest entry.
• When you disable Node Alias on a port, clients learned on that port are deleted unless the port is a member of an MLT with at least one port with Node Alias enabled. If the MLT has no ports with Node Alias enabled, the entries are deleted.